home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93c.txt
/
000087_icon-group-sender _Sun Nov 14 10:59:33 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-02-02
|
3KB
Received: by cheltenham.cs.arizona.edu; Mon, 15 Nov 1993 09:05:48 MST
Date: 14 Nov 93 10:59:33 GMT
From: noc.near.net!news.delphi.com!usenet@uunet.uu.net (Will Mengarini)
Organization: Delphi Internet
Subject: Re: dos executables from icon
Message-Id: <931114.21573.MENGARINI@delphi.com>
References: <93312.000307U47041@uicvm.uic.edu>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
I have implemented a system for doing this. I e-mailed
the Icon Project 2 months ago to tell them about it,
then Ralph Griswold a month later, but in neither case
did I get a reply; Griswold is on sabbatical thru 1994,
& the I.P. never answered.
During the process of coding my implementation for producing
a DOS .Exe file using IconT, I discovered that there was
code #ifdeffed out that seemed to implement the same kind
of thing on other operating systems, but vital components
of that "header" subsystem are not included in the MS-DOS
distribution. There's other stuff that's also not included;
I don't know what "the variant translator subsystem" is since
I've never seen it, but I have a whole list of changes I want
to make to the language, & it'll be a real pain to be reinventing
a wheel unnecessarily. I get the feeling MS-DOS is treated with
too much contempt by the Icon Project; sure it's dumb, but it's
ubiquitous, & now it's typically used on very powerful hardware
that, in protected mode, can offer a 16M address space & lots
of disk space. Any system that can handle C++ can handle the
full Icon system, & omitting essential stuff like these
items from the distribution is really inconveniencing a
large group of potential users. Mistakes like these might
explain why there's so little activity in the newsgroup of
such a brilliant language.
For my next trick, I want to rebuild Icon{T,X} to run in
protected mode under Phar Lap's 16-bit DOS extender. I wouldn't
be surprised if somebody has done this already; if so, please
post your Make file. I'll try to also integrate my .Exe system
with that, but your Make file will help as a starting point even
if you haven't worked on the .Exe problem.
Because I got no response from the Icon Project & concluded
nobody was home, I assumed there was no interest in an adaptation
to handle .Exe files, & I haven't packaged it into something easily
distributable. I'll start working on that, but it'll take a week or two;
I typically spend an entire week sleeping at the office, & I only get
onto this newsgroup on weekends, so I can't do it any faster.
Also, has anybody else solved the MS-DOS .Exe problem?
We could compare notes.